Selecting Group 1 (Holding type) or Group 2 (General) from the Publication pattern screen results in the system displaying the Edit publication pattern form.
Description – description field from the type of holding record.
Supplier number – the supplier’s reference number can be entered on this form only if it was not assigned at the subscription level. In the case that it is added at this level, an index search using the supplier reference number will be able to determine the type of holding that is being received.
Status – Active – the publication pattern is active. Inactive – the publication pattern has been superseded and is no longer in use.
Enumeration – defines the numbering of the predicted issues. The system allows you to define seven levels of enumeration. For each level, there are four fields that work together to define how the numbering is predicted.
1. Captions –specify a caption for each level you want to use. Make sure you include punctuation. Most patterns have at least one level. Enclose this text in round brackets or square brackets to suppress the display of the text when enumeration is displayed. Enclose this text in curly brackets if you do not wish to see the information for a particular level display at all when predictions are displayed. In this situation, the enumeration level is created to allow accurate predictions but you do not want to include this level when the predicted issues display. For example, if you have a publication with numbering that includes two numbers (i.e. v. and no.) and you want to predict 2 subsequent issues with the same enumeration and differing chronology, create a third level of enumeration (i.e. pt.) and enclose the caption with curly brackets, set the number of parts to 2 and set the numbering code to reset. The system will predict something similar to the following: v.23:no.2(2003:February), v.23:no.2(2003:March), v.23:no.3(2003:April).
2. Enumeration code (*) – defines whether the predicted numbering at the selected level is a number, alphabetic, roman numeral or a constant. Select F8 (or type in ?L) to see and choose from the list of valid codes. Enumeration codes are defined in section 367.2.8.
3.
Number of parts – defines how many units at the selected level make up the higher level. Used by the system when predicting issues, for determining when to increment the next higher level’s counter. Specify a number for each level of enumeration except the first .In the example, twelve no. (issue) units make up one v. (volume).
4. Numbering code (*) – defines whether numbering at the selected level increments indefinitely or restarts when the next highest unit increments. For example, after v.25:iss.12 is received, should the system predict v.26:iss.13 (continuous) or v.26:iss.1 (restart/reset). Select F8 (or type in ?L) to see and choose from the list of valid codes. Numbering codes are defined in section 367.2.7.
Chronology – date information that identifies the published issue. The system allows you to define up to four levels of chronology. For each level, there are two fields that work together to define how the date information is predicted.
1. Captions – Enter the caption or label. Enclose this text in round brackets or square brackets to suppress the display of the text when chronology is displayed. For example, (year.) (mo.) (d.) is replaced by 2005:NOV:15. Used by the system as entry prompts and display in holdings statements, parts lists, and serials holdings display.
2. Chronology code (*) – Specify a Chronology Code. Specifies the kind of chronological data at this chronology level; e.g. year (YYYY format), month (MMM format), date (MM/DD/YY format). Select F8 (or type in ?L) to see and choose from the list of valid codes. Used by the system to generate data in holdings statements and to edit-check data entered by the user. Chronology codes are defined in section 367.2.5.
Base level - The base enumeration level usually the lowest level but in some month-based patterns the next-to-lowest level. Used by the system when predicting issues, for determining whether a change in month should reset the numbering. The numbering of the lowest and next-to-lowest levels are also affected by the lowest level’s Numbering code and Number of parts.
· Setting the Base level to the lowest level - If you set the Base level to the lowest level (such as 2 in the sample screen), then a change in month will not automatically reset the lowest level’s numbering. If the lowest level’s Numbering code is continuous, then the level’s numbering continues to increase indefinitely. If the code is restart/reset, then the level’s numbering is reset every M issues (where M = number of parts). In either case, the next higher level’s numbering is incremented every M issues.
· Setting the base level to the next-to-lowest level - If you set the Base level to the next-to-lowest level (such as 2 in the 3-level serial), then the system can handle patterns with different numbers of issues published each month. If the lowest level’s Numbering code is continuous, then that level’s numbering increases indefinitely. If the code is restart/reset, then that level’s numbering is reset each time a new month begins (or every M issues, whichever comes first). In either case, the next higher level’s numbering is incremented each time a new month begins (or every M issues, whichever comes first).
Frequency – Describes the frequency of publication and is selected from either the frequency code list from the MARC21 or UNIMARC standard. These codes are for information purposes only with the exception of five codes which are interpreted by the system: biennial – repeat regularity pattern every 2 years, triennial – repeat regularity pattern every 3 years, quadrennial – every 4 years, quinquennial – every 5 years and decennial – every 10 years. The system uses this information when predicting the years of expected issues. Frequency codes are defined in section 367.9.
Frequency notes – A note about the publication pattern. For example, Monthly with an extra issue in May and October; 14 issues per volume and continuously incrementing issue numbers.
Autopredict – If checked, the system predicts the enumeration, chronology, and expected receipt dates. Predictions display on the View predictions form. Leave unchecked if the pattern is too erratic to predict. The Numbering that you define on the Serial predictions form will be repeated for all expected issues.
Compress holdings – Indicates whether the holdings data can be compressed or expanded by computer algorithm. If checked, holdings statements will include ranges of held issues (i.e. v.1-v.5). If left unchecked (or in the case of Indexes), holdings statements will include a list of each held issue (i.e. v.1,v.2,v.3,v.4,v.5)..
Date range - range of enumeration and chronology to which the pattern applies. For example, Vol.23 No.2- (1991:February- )for a pattern whose prediction start issue was the February 1991 issue. Before you use the Copy option to inactivate the current publication pattern and create a new active publication pattern, you may add the closing issue’s enumeration and chronology here. This information is stored but not otherwise used by the system.